Re-using e-commerce payment instruments for in-store use systems and methods

ABSTRACT

Provided are a re-using e-commerce payment instruments for in-store purchasing systems and methods. A customer enters a check out and a transaction at the point of sale is started. The system receives a pairing request at a wallet processor from a customer mobile device operating a mobile application. This pairing request is created and sent in response to scanning of a code having a transaction identification. The system associates a customer payment profile with the transaction identification and sends associated information to the point of sale. The point of sale sends an amount of sale to authorize to the wallet processor after completing scanning of items. The system creates an authorization for payment and sending the authorization for payment to an authorizer. The transaction may then be completed by processing payment.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation application of U.S. application Ser.No. 15/767,487, filed Apr. 11, 2018, which is a national stage entry ofPCT/US2015/055134, filed Oct. 12, 2015, and the disclosures of which areincorporated by reference herein in their entirety.

FIELD OF THE INVENTION

The invention relates generally to payment instruments, and morespecifically, to systems and methods for re-using e-commerce paymentinstruments for in-store purchasing of items.

BACKGROUND

Many customers have discount cards, membership cards, and paymentinstruments they carry in a wallet or purse. These customers may havealready loaded their personal data, discount cards, membership card andpayment instruments in their e-commerce/mobile customer profile with aparticular business. Mobile electronic payment systems require customersto re-enter that information into an application or other system inorder to provide payment in-store from a mobile application.

BRIEF SUMMARY

In one aspect, provided is a method for paying at a point of salecomprising: starting a transaction at the point of sale; receiving apairing request at a wallet processor from a customer mobile deviceoperating a mobile application in response to scanning of a code havinga transaction identification; associating a customer payment profilewith the transaction identification and sending associated informationto the point of sale; sending an amount of sale to authorize to thewallet processor in response to completing scanning of items at thepoint of sale; creating an authorization(s) for payment and sending theauthorization for payment to an authorizer; and completing thetransaction by processing payment.

In another aspect, provided is a method for paying at a point of salecomprising: starting a transaction at the point of sale; receiving apairing request at a wallet processor from a customer mobile deviceoperating a mobile application in response to transmitting a transactionidentification from a wireless device of the point of sale to thecustomer mobile device; associating a customer payment profile with thetransaction identification and sending associated information to thepoint of sale; sending an amount of sale to authorize to the walletprocessor in response to completing scanning of items at the point ofsale; creating an authorization for payment and sending theauthorization for payment to an authorizer; and completing thetransaction by processing payment.

In another aspect, provided is a system for re-using e-commerce paymentinstruments for in-store purchasing, the system comprising: a backendsystem including a wallet processor and a memory, wherein the memorystores a customer payment profile comprising an already establishede-commerce payment profile; a mobile device in communication with thewallet processor; a point of sale in communication with the walletprocessor and the mobile device, wherein the mobile device operates amobile application to communicate with the wallet processor to associatea transaction identification from the point of sale with the customerpayment profile; and an authorizer for authorizing a payment of anamount of sale in response to receiving the amount of sale from thewallet processor.

BRIEF DESCRIPTION OF THE SEVERAL VIEWS OF THE DRAWINGS

The above and further advantages of this invention may be betterunderstood by referring to the following description in conjunction withthe accompanying drawings, in which like numerals indicate likestructural elements and features in various figures. The drawings arenot necessarily to scale, emphasis instead being placed uponillustrating the principles of the invention.

FIG. 1 is a block diagram of a system for re-using e-commerce paymentinstruments for in-store purchasing, in accordance with embodiments.

FIG. 2 is a flow diagram illustrating a method for creating ane-commerce account, in accordance with some embodiments.

FIG. 3 is a flow diagram illustrating a method for setting up e-commercepayments instruments for use in-store, in accordance with someembodiments.

FIG. 4 is a flow diagram illustrating a method for executing atransaction at a store checkout using a system for re-using e-commercepayment instruments for in-store purchasing, in accordance with someembodiments.

FIG. 5 is a flow diagram illustrating another method for executing atransaction at a store checkout using a system for re-using e-commercepayment instruments for in-store purchasing, in accordance with someembodiments.

DETAILED DESCRIPTION

Many store customers have times when they shop online and other timeswhen they are physically present at a brick-and-mortar store. In orderto shop online, a customer must establish an e-commerce account with theparticular business which often includes entering and storing paymentinstruments in a database for use with the that particular business.This provides ease of checking out at the end of an online shoppingsession, wherein the customer can simply execute a few mouse clicks orother input, such as use of a touchscreen and the like, to executepayment to complete an online transaction. Sometimes the paymentinstruments are stored for future re-use as part of checking out andcompleting an order.

Shopping in a brick-and-mortar store requires the customer must movearound and peruse items and goods with the store, select the goods,often putting them within a cart and then proceeding to a checkout line,where a point of sale terminal is then used to scan or otherwise totalthe amount of money due to purchase the items. The customer must thenretrieve the payment instrument from his or her wallet or purse andprovide the payment instrument to the point of sale terminal. If apayment card is the type of payment instrument, the card is eitherswiped by the customer or the employee at the checkout and the paymentis processed either by entering a personal identification number (“PIN”)or signing to authorize the payment, thus completing the transaction.Online customers enjoy an expedient check out that is typically notoffered at a brick-and-mortar store. The present inventive conceptsprovide the benefits of online checkout processes with in-store shoppingwithout the need for re-entering payment instruments within a mobileapplication on a mobile device. For example, the customer can use apayment instrument already saved in the customer's e-commerce accountwith a business to pay for a transaction that occurs in abrick-and-mortar store of the same business.

FIG. 1 is a block diagram of a system 10 for re-using e-commerce paymentinstruments for in-store purchasing. The system 10 may include a backendsystem having various databases, such as, but not limited to useraccounts 14, payment accounts 16, non-payment cards/identifiers 18,payment preferences 20, and payment rules 21. These databases 14, 16, 18and 20 are accessible from an e-commerce application 12. Further, thedatabases 14, 16, 18 and 20 are accessible from a mobile application 22.The system 10 may also include a wallet processor 24, a point of sale(“POS”) 26, a payment gateway 27 and an authorizer(s) 28. The walletprocessor 24 may have access to payments accounts 16, non-paymentcards/identifiers 18, payment preferences 20, and payment rules 21databases. The e-commerce application 12 may be accessible through acomputing device, such as but not limited to a computer, a laptop, atablet, a smartphone and the like. The e-commerce application 12 may bean e-commerce website accessible through an Internet connection. Themobile application 22 may be accessible through a mobile device, such asa smartphone, a tablet and the like. The mobile application 22 may be adownloadable application that is installed and operated on the mobiledevice. The payment gateway 27 may operate to send messages routed tothe authorizers 28.

Referring additionally to FIG. 2 , the system 10 may be utilized toexecute a method 30 of creating an e-commerce account. The method 30 mayinclude operating an e-commerce application 12 from a computing device(Step 31); entering user information including customer name, address,user name and password (Step 32); and saving the user information in theuser accounts 14 database (Step 33). The method 30 may further includeentering a payment instrument information through the e-commerceapplication 45 and storing the payment instrument information in thepayment accounts 16 database. The method 30 may also include enteringnon-payment card/identifier information through the e-commerceapplication 12 and storing the non-payment card/identifier informationin the non-payment cards/identifier 18 database. It will be understoodthat the method 30, in some embodiments, is a precondition to using thesystem to complete a transaction at a POS 26.

Further, access to the user accounts 14, payment accounts 16,non-payment cards/identifiers 18 and payment preferences 20 databasesare secured by restricting access to the information. The username andpassword stored in the user accounts 14 database includes theinformation that must be input through a user graphical interface inorder for a customer to login to his or her e-commerce account toaccess, update, change and the like the information stored in the useraccounts 14, payment accounts 16, non-payment cards/identifiers 18, andpayment preferences 20 databases. The customer may login to thee-commerce account through the e-commerce application 12 or through themobile application 22.

It is anticipated that the user account 14 may be changed and updated atany time through use of the e-commerce application 12 or the mobileapplication 22. For example, address information may be updated,additional payment instruments may be added to the payment accounts 16,and additional non-payment cards may be added to the non-paymentcards/identifier 18. Further, as payment instruments expire, the paymentinstrument information stored in the payment accounts 16 may be updatedor removed.

FIG. 3 depicts a method 40 of setting up e-commerce payments instrumentsfor in-store use. For example, the method 40 may include logging intothe e-commerce account (Step 41) through the mobile application 22 orthrough the e-commerce application 12; activating mobile in-storepayment functionality (Step 42), wherein activating the mobile in-storepayment functionality requires creating a new payment authenticationcode, such as a PIN, password and the like; and selecting an existingpayment instrument stored in the payment accounts 16 for use in mobilein-store payment (Step 43). This information may be stored in thepayment preferences 20.

Step 43 of selecting an existing payment instrument may be repeated toselect multiple payment instruments for use with mobile in-storepayments. If multiple payment instruments are selected, the customer mayalso indicate how he or she prefers to use the payment instruments whenconducting transactions in the store.

The method 40 may also include entering a new payment instrument throughthe mobile application 22 and indicating if it may also be used fore-commerce transactions and/or how the customer prefers to use thepayment instrument when transacting in the store.

The method 40 may also include presenting a list of existing non-Paymentcards/identifiers (e.g. Membership, Loyalty, Discount, Offers) to acustomer and selecting which non-payment cards/identifiers to load formobile in-store processing. This may be repeated if there are multiplenon-payment cards on file. The method may also include entering newnon-Payment cards/identifiers to the non-payment cards/identifiers 18database and selecting it to be used for e-commerce transactions or whentransacting in the store.

FIG. 4 depicts a method 50 for executing a transaction at a storecheckout using a system for re-using e-commerce payment instruments forin-store purchasing. The method 50 may include starting a transaction atthe POS 26 (Step 51); receiving a pairing request at a wallet processor24 from a customer mobile device operating a mobile application 22 inresponse to scanning of a code having a transaction identification (Step52); associating a customer payment profile with the transactionidentification and sending associated information to the POS (Step 53);sending an amount of sale to authorize to the wallet processor inresponse to completing scanning of items at the POS (Step 54); creatingan authorization for payment and sending the authorization for paymentto an authorizer 28 (Step 55); and completing the transaction byprocessing payment (Step 56).

In a method 50, the customer payment profile may comprise an alreadyestablished e-commerce payment profile stored in a payment preferences20 database. Further, the customer payment profile may further compriseone or more payment instruments stored in the payment accounts 16database.

The scanning of the code of Step 52 may include scanning the codegenerated by the POS 26. In another embodiment, scanning the code maycomprise scanning the code generated by the customer mobile device witha scanning device at the POS 26.

The method 50 may further comprise designating one payment instrument ofthe one or more payment instruments in the customer payment profile as adefault payment instrument prior to starting the transaction. The method50 may also comprise alerting the wallet processor that the transactionis complete; and alerting the mobile device from the wallet processorthat the transaction is complete.

FIG. 5 depicts a method 60 for executing a transaction at a storecheckout using a system for re-using e-commerce payment instruments forin-store purchasing in accordance with embodiments. A method 60 mayinclude starting a transaction at the POS 26 (Step 61); receiving apairing request at a wallet processor from a customer mobile deviceoperating a mobile application in response to transmitting a transactionidentification from a wireless device of the POS 26 to the customermobile device (Step 62); associating a customer payment profile with thetransaction identification and sending associated information to the POS26 (Step 63); sending an amount of sale to authorize to the walletprocessor in response to completing scanning of items at the POS 26(Step 64); creating an authorization for payment and sending theauthorization for payment to an authorizer 28 (Step 65); and completingthe transaction by processing payment (Step 66).

In method 60 the customer payment profile comprises an alreadyestablished e-commerce payment profile stored in a payment preferences20 database. The customer payment profile may also comprise one or morepayment instruments stored in a payment accounts 16 database.

The method 60 may further comprise designating one payment instrument ofthe one or more payment instruments in the customer payment profile as adefault payment instrument prior to starting the transaction. The method60 may also comprise alerting the wallet processor that the transactionis complete and alerting the mobile device from the wallet processorthat the transaction is complete.

Transmitting the transaction identification from the wireless device tothe customer mobile device of Step 63 comprises transmitting with aBluetooth low energy communication. Further, transmitting thetransaction identification from the wireless device to the customermobile device may comprise transmitting with a near field communication.Further still, transmitting the transaction identification from thewireless device to the customer mobile device comprises transmittingdata with a radio frequency communication.

Step 65 of sending an authorization for payment to the authorizer 28 mayalso include sending an authorization for payment to a payment gateway27. The payment gateway 27 may then send the authorization for paymentto the authorizer(s) 28. The payment gateway 27 may operate to controlthe sending of the authorizations to the authorizer(s) 28.

Referring additionally to FIG. 1 , in performing the method 50, the POS26 creates a unique transaction/basket ID. The POS 26 may display acode, such as a one-dimensional barcode or QR code that includes theunique transaction/basket ID for the customer to capture with his or hermobile device operating the mobile application 22. In some otherembodiments, the unique transaction/basket ID may be transmittedwirelessly (e.g. BLE), to the customer's mobile device.

In order for the customer's mobile device to scan the code from thedisplay, a customer may log in using the mobile application operating onthe mobile device and navigates to a payment feature. The customer maythen provide the Payment Authentication Code (e.g. PIN, password, etc.)in order to validate the payment feature. The customer may then capturetransaction/basket ID from the code created by the POS 26.

In order for the customer's mobile device to obtain the uniquetransaction/basket ID wirelessly, a wireless message is sent from thePOS 26 to the mobile device of the customer. When the message isreceived, the customer is asked through the mobile device operating themobile application 22 if he or she wishes to use the payment feature. Ifthe customer wishes to use the payment feature, the customer may selectso using the mobile application and the mobile application 22automatically navigates to the payment feature and the customer mayprovide the Payment Authentication Code (e.g. PIN, password, etc.) inorder to validate the payment feature.

The mobile application 22 alerts the wallet processor 24 of a pairingrequest, wherein the wallet processor 24 gathers customer/payment/carddata and sends the customer/payment/card data to the POS 26. The POS 26completes scanning items and sends amount to authorize to walletprocessor after verbal confirmation of the amount to be paid by thecustomer.

The wallet processor 24 uses the payment preferences, payment rules 21and payment instruments to create one or more authorizations and sendsthem to the authorizer 28. The wallet processor 24 then sends theresponses to the POS 26. The POS 26 completes the transactions andalerts the wallet processor 24 that the transaction is complete. Thewallet processor 24 may then alert the mobile device that thetransaction is complete in order to alert the customer.

In another embodiment, a customer may log in using a mobile application22 and navigate to a payment feature. The customer may then providePayment Authentication Code (e.g. PIN, password, etc.) in order tovalidate the payment feature. The mobile application 22 may thenretrieve a transaction/basket ID from the wallet processor 24. Themobile application 22 encodes the transaction/basket ID and displayseither one-dimensional barcode or QR code having the transaction/basketID. The POS 26 may then scan the transaction/basket ID.

The POS 26 alerts the wallet processor 24 of a pairing request, and thewallet processor gathers customer/payment/card data and sends thecustomer/payment/card data to the POS 26. The POS 26 may completescanning items and send an amount owed to be authorized to the walletprocessor 24. The wallet processor 24 uses the payment instrumentsstored in the payment accounts 16, payment preferences 20 and paymentrules 21 databases to create one or more authorizations and send them tothe authorizer 28. The wallet processor 24 sends responses to the POS26. The POS 26 completes the transaction and alerts the wallet processor24 that the transaction is complete. The wallet processor 24 may thenalert the mobile device that the transaction is complete in order toalert customer.

As will be appreciated by one skilled in the art, aspects of the presentinvention may be embodied as a system, method, or computer programproduct. Accordingly, aspects of the present invention may take the formof an entirely hardware embodiment, an entirely software embodiment(including firmware, resident software, micro-code, etc.) or anembodiment combining software and hardware aspects that may allgenerally be referred to herein as a “circuit,” “module” or “system.”Furthermore, aspects of the present invention may take the form of acomputer program product embodied in one or more computer readablemedium(s) having computer readable program code embodied thereon.

Any combination of one or more computer readable medium(s) may beutilized. The computer readable medium may be a computer readable signalmedium or a computer readable storage medium. A computer readablestorage medium may be, for example, but not limited to, an electronic,magnetic, optical, electromagnetic, infrared, or semiconductor system,apparatus, or device, or any suitable combination of the foregoing. Morespecific examples (a non-exhaustive list) of the computer readablestorage medium would include the following: an electrical connectionhaving one or more wires, a portable computer diskette, a hard disk, arandom access memory (RAM), a read-only memory (ROM), solid-state drives(SSD), an erasable programmable read-only memory (EPROM or Flashmemory), an optical fiber, a portable compact disc read-only memory(CD-ROM), an optical storage device, a magnetic storage device, or anysuitable combination of the foregoing. In the context of this document,a computer readable storage medium may be any tangible medium that cancontain, or store a program for use by or in connection with aninstruction execution system, apparatus, or device.

A computer readable signal medium may include a propagated data signalwith computer readable program code embodied therein, for example, inbaseband or as part of a carrier wave. Such a propagated signal may takeany of a variety of forms, including, but not limited to,electro-magnetic, optical, or any suitable combination thereof. Acomputer readable signal medium may be any computer readable medium thatis not a computer readable storage medium and that can communicate,propagate, or transport a program for use by or in connection with aninstruction execution system, apparatus, or device.

Program code embodied on a computer readable medium may be transmittedusing any appropriate medium, including but not limited to wireless,wire-line, optical fiber cable,

RF, etc., or any suitable combination of the foregoing.

Computer program code for carrying out operations for aspects of thepresent invention may be written in any combination of one or moreprogramming languages, including an object oriented programming languagesuch as Java, Smalltalk, C++or the like and conventional proceduralprogramming languages, such as the “C” programming language or similarprogramming languages. The program code may execute entirely on theuser's computer, partly on the user's computer, as a stand-alonesoftware package, partly on the user's computer and partly on a remotecomputer or entirely on the remote computer or server. In the latterscenario, the remote computer may be connected to the user's computerthrough any type of network, including a wireless network, a cellulardata network, a local area network (LAN) or a wide area network (WAN),or the connection may be made to an external computer (for example,through the Internet using an Internet Service Provider).

Aspects of the present invention are described herein with reference toflowchart illustrations and/or block diagrams of methods, apparatus(systems) and computer program products according to embodiments of theinvention. It will be understood that each block of the flowchartillustrations and/or block diagrams, and combinations of blocks in theflowchart illustrations and/or block diagrams, can be implemented bycomputer program instructions. These computer program instructions maybe provided to a processor of a general purpose computer, specialpurpose computer, or other programmable data processing apparatus toproduce a machine, such that the instructions, which execute via theprocessor of the computer or other programmable data processingapparatus, create means for implementing the functions/acts specified inthe flowchart and/or block diagram block or blocks.

These computer program instructions may also be stored in a computerreadable medium that can direct a computer, other programmable dataprocessing apparatus, or other devices to function in a particularmanner, such that the instructions stored in the computer readablemedium produce an article of manufacture including instructions whichimplement the function/act specified in the flowchart and/or blockdiagram block or blocks.

The computer program instructions may also be loaded onto a computer,other programmable data processing apparatus, cloud-based infrastructurearchitecture, or other devices to cause a series of operational steps tobe performed on the computer, other programmable apparatus or otherdevices to produce a computer implemented process such that theinstructions which execute on the computer or other programmableapparatus provide processes for implementing the functions/actsspecified in the flowchart and/or block diagram block or blocks.

The flowchart and block diagrams in the Figures illustrate thearchitecture, functionality, and operation of possible implementationsof systems, methods and computer program products according to variousembodiments of the present invention. In this regard, each block in theflowchart or block diagrams may represent a module, segment, or portionof code, which comprises one or more executable instructions forimplementing the specified logical function(s). It should also be notedthat, in some alternative implementations, the functions noted in theblock may occur out of the order noted in the figures. For example, twoblocks shown in succession may, in fact, be executed substantiallyconcurrently, or the blocks may sometimes be executed in the reverseorder, depending upon the functionality involved. It will also be notedthat each block of the block diagrams and/or flowchart illustration, andcombinations of blocks in the block diagrams and/or flowchartillustration, can be implemented by special purpose hardware-basedsystems that perform the specified functions or acts, or combinations ofspecial purpose hardware and computer instructions.

While the invention has been shown and described with reference tospecific preferred embodiments, it should be understood by those skilledin the art that various changes in form and detail may be made thereinwithout departing from the spirit and scope of the invention as definedby the following claims.

1. A method for paying at a point of sale, comprising: receiving, from amobile device via a mobile application of a business for in-storepayments, user login associated with an account stored in a useraccounts database of the business, the account being previouslyestablished with the business for making purchases from the business andincludes a payment profile; retrieving, from a payment accounts databaseof the business, payment instrument information from the paymentprofile; causing the mobile application to display for selection, one ormore payment instruments associated with the payment profile to add asan in-store payment instrument; receiving, via the mobile application, aselection to use a payment instrument from the payment profile forin-store payments at a brick-and-mortar store of the business; storing,in a payment preferences database of the business, the paymentinstrument selected from the payment profile as a default paymentinstrument of the account for in-store payments at the business, whereininformation associated with the account in the user accounts database,the payment accounts database, and the payment preferences database aresecured for access by the user login associated with the accountestablished with the business; starting a transaction at the point ofsale in the brick-and-mortar store of the business; receiving, at awallet processor, a pairing request identifying the account logged intothe mobile application; associating the payment profile with thetransaction, wherein the payment profile comprises informationassociated with the payment instrument according to the paymentpreferences database for in-store payments; sending an amount of sale toauthorize to the wallet processor in response to completing scanning ofitems at the point of sale; creating an authorization for payment andsending the authorization for payment to an authorizer; and completingthe transaction by processing payment.
 2. The method of claim 1, whereinthe payment profile comprises the one or more payment instruments. 3.The method of claim 1, wherein sending an authorization for payment tothe authorizer comprises sending the authorization for payment to apayment gateway, wherein the payment gateway sends the authorization forpayment to the authorizer.
 4. The method of claim 1, further comprisingalerting the wallet processor that the transaction is complete.
 5. Themethod of claim 4, further comprising alerting the mobile device fromthe wallet processor that the transaction is complete.
 6. The method ofclaim 1, wherein associating the payment profile with the transaction isbased on the user device scanning a code generated by the point of sale.7. The method of claim 1, wherein associating the payment profile withthe transaction is based on the user point of sale scanning a codegenerated by the mobile device with a scanning device of the point ofsale.
 8. A method for paying at a point of sale, comprising: receiving,from a mobile device via a mobile application for in-store payments,user login associated with an account stored in a user accounts databaseof a business, the account being previously established with thebusiness for making purchases from the business and includes a paymentprofile; retrieving, from a payment accounts database of the business,payment instrument information from the payment profile; causing themobile application to display for selection, one or more paymentinstruments associated with the payment profile to add as an in-storepayment instrument; receiving, via the mobile application, a selectionto use a payment instrument from the payment profile for in-storepayments at a brick-and-mortar store of the business; storing, in apayment preferences database of the business, the payment instrumentselected from the payment profile as a default payment instrument of theaccount for in-store payments at the business, wherein informationassociated with the account in the user accounts database, the paymentaccounts database, and the payment preferences database are secured foraccess by the user login associated with the account established withthe business; starting a transaction at the point of sale in thebrick-and-mortar store of the business; receiving, at a walletprocessor, a pairing request identifying the account logged into themobile application; associating the payment profile with thetransaction, wherein the payment profile comprises informationassociated with the payment instrument according to the paymentpreferences database for in-store payments; sending an amount of sale toauthorize to the wallet processor in response to completing scanning ofitems at the point of sale; creating an authorization for payment andsending the authorization for payment to an authorizer; and completingthe transaction by processing payment.
 9. The method of claim 8, whereinthe payment profile comprises one or more payment instruments.
 10. Themethod of claim 8, wherein sending an authorization for payment to theauthorizer comprises sending the authorization for payment to a paymentgateway, wherein the payment gateway sends the authorization for paymentto the authorizer.
 11. The method of claim 8, further comprisingalerting the wallet processor that the transaction is complete.
 12. Themethod of claim 8, further comprising alerting the mobile device fromthe wallet processor that the transaction is complete.
 13. A system forre-using payment instruments for in-store purchasing, the systemcomprising: a backend system including a wallet processor and a memory,wherein the memory stores a user accounts database, a payment accountsdatabase, and a payment preferences database of a business , and whereinthe backend system is configured to: receive, from a mobile device via amobile application for in-store at the business, user login associatedwith an account stored in the user accounts database of the business,the account being previously established with the business for makingpurchases from the business and includes a payment profile; retrieve,from the payment accounts database of the business, payment instrumentinformation from the payment profile; cause the mobile application todisplay for selection, one or more payment instruments associated withthe payment profile to add as an in-store payment instrument; receive,via the mobile application, a selection to use a payment instrument fromthe payment profile for in-store payments at a brick-and-mortar store ofthe business; and store, in the payment preferences database of thebusiness, the payment instrument selected from the payment profile as adefault payment instrument for in-store payments at the business,wherein information associated with the account in the user accountsdatabase, the payment accounts database, and the payment preferencesdatabase are secured for access by the user login associated with theaccount established with the business; and a point of sale in thebrick-and-mortar store of the business in communication with the walletprocessor and the mobile device, wherein the wallet processor isconfigured to associate a transaction from the point of sale with thepayment profile of the account logged into the mobile application. 14.The system of claim 13, wherein the memory of the backend system furtherincludes a non-payment cards/identifiers database.
 15. The system ofclaim 14, wherein the wallet processor accesses the user accountsdatabase, the payment accounts database, the non-paymentcards/identifiers database, payment rules database and the paymentpreferences database to obtain the payment profile.
 16. The system ofclaim 13, further comprising a payment gateway, wherein the paymentgateway receives authorizations for payment and sends the authorizationsfor payment to an authorizer.